home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
iput1103.zip
/
RTMDR114.ZIP
/
RTG2MDIR.DOC
< prev
next >
Wrap
Text File
|
1991-03-10
|
12KB
|
361 lines
RTG2MDIR ROUTING.BBS -> GTMDIR.BBS
Version 1.14
The guff at the start
Ever get fed up with ensuring that ROUTING, and GTMDIR are both kept
uptodate?... checking every week or so to see what is new, and what
echoes have closed down?... pain in the ar*e isn't it?.. So, here is
a partial solution to the problem, RTG2MDIR will build GTMDIR for you
using the data available in your ROUTING and the status of the echoes
being read in from ECHLIST.BBS. That way, you keep track of the temp
down, retired etc echoes, as they will be listed in the appropriate
GTMDIR.???. The composite GTMDIR.BBS available for your users will
have all the various specialist echoes all grouped together etc
Even more junk... better read this bit though
---------------------------------------------
----------------
-> Guarantee <-
----------------
You're kidding right?.... a fiver says you ain't paid owt for this -
so as you lose, send me a fiver ( US$10 ) and that'll do me fine for
registration.
The software is guaranteed to do nothing except occupy several KBytes
of disk space, and if executed, take up a little RAM, which it might
free for later use, if it terminates without hanging.
----------
Disclaimer
----------
A sign of the times I suppose, you gotta have this or someone will
try it on.
The author accepts no responsibility for any of the results caused by
possesion of, or execution of the program, written and distributed by
me as RTG2MDIR.
If anything happens at all, then it isn't my fault, no responsibility
can, or will, be accepted for any results whatsoever which may or may
not be be directly or indirectly traced to the presence and / or the
execution of this program.
-----------------------------
What's it do then?.
Reading in GTMDIR.BBS from GTPATH directory, and ROUTING.BBS - also
from GTPATH, a series of files will be built up, each named GTMDIR
with the extension E00, E01 etc, contents will be the sections of
GTMDIR.BBS containing the E01, E02 etc etc echoes.
│ All files written are placed in a sub-directory RTG2MDIR.WRK which is
│ created off GTPATH.
│ The echo descriptions which are placed in the GTMDIR.??? files in the
│ work directory are will be taken from the following sources:-
│ file specified on command line ( ECHOLIST format ),
│ if no file specified on comamnd line, then the
│ config file will be checked for a source, if none
│ is given there, then ECHOLIST.BBS in your GTPATH
│ will be used.
│ if none of the above files can be opened, then the descriptions
│ will be taken from GTMDIR.BBS in the GTPATH.
│ if GTMDIR.BBS cannot be opened, then the echo descriptions will
│ then be taken from the ROUTING.BBS.
│ This gives a multitude of source of echo descriptions. ECHOLIST is
│ the best, because that allows standardisation of echo descriptions.
Command line Switches
/split this option will read ROUTING.BBS, GTMDIR.BBS and also
ECHOLIST.BBS from the GTPATH directory and create a few
files are then created, the name is GTMDIR, and with the
extension will be the three letters of the echo groups
that are found in ROUTING.BBS, e.g GTMDIR.E02 etc.
IF the pharase FIDO appears in the description of the
echo in ROUTING.BBS, then it will always be placed in
GTMDIR.DOG regardless of whether /CAT ( see below ) is
used.
NOTE
these files will overwrite any existing files.
These files will be in the normal GTMDIR.BBS format,
with access level, directory and description on the
one line.
If ECHOLIST.BBS cannot be found, then the descriptions
will be extracted from the existing GTMDIR.BBS, along
with the access level to the message base.
When GTMDIR isn't available, then the message base
description and the path are taken from those details
specified in ROUTING.BBS, and the access level to be
associated with each echo is as specified in config
file with the ACCESS parameter, if this has not been
│ specified there, then it defaults to 'A'.
Private, public, netmail, and readonly message bases
are catered for, as are those flagged as temp down,
retired, renumbered, new sponsor, unknown sponsor
etc etc in ECHOLIST.BBS ( new hours is the only one
I'm not interested ). Oh, and don't worry about any
password encrypted echoes, these should be handled
OK in the situation where the echo description is
taken from ROUTING.BBS, but don't take my word for it,
check!.
/cat added this because the ECHOLIST format was changed,
and a 'new' field added, a three letter category for
the echoes, e.g. SPT - Sport, CHT - chat etc etc, so
might as well let you sort our GTMDIR list by echo
subject, without you having to trail through them all.
There may be the case where an echo is listed in the
GTMDIR and ROUTING, but has no entry in ECHOLIST, in
the UK this is rlevant to the E30 echoes. If the /CAT
switch is used, then these echoes will be listed in
GTMDIR._#_, yeah, I know it's a wierd extension, but
can *you* think of something that others might not be
using?.
/missing as /SPLIT, except does not write the GTMDIR.Exx files.
just lists inconsistencies.
/build builds a replacement for GTMDIR.BBS from the GTMDIR.xxx
files found in the GTPATH directory. The order in which
the files are added is the same as the order in which the
extensions are specified in the config file. Any files
whose extensions are NOT listed in the config file are
not added, but the extensions will be listed when the
build has completed.
│ Will automatically /split if no GTMDIR files are found
│ in the working directory.
/source=d:\path\filename.ext
if specified this is the file where the descriptions
for the message bases are found. This file must be in
the same format as ECHOLIST.BBS, either the new or the
old format. If not specified on the command line, will
default to ECHOLIST.BBS in GTPATH, unless it is given
in RTG2MSIR.CFG, e.g. command line overrides whatever
is given in the config file.
If the file specified with the /SOURCE switch can not
be opened, then the required data ( echo descriptions )
will be those found in GTMDIR.BBS.
Note that if GTMDIR cannot be opened, then the echo
descriptions will be those you have given in your
ROUTING.BBS
│ /welcome[=d:\path\filename.ext]
│ creates a WELCOME.BBS in each message area. The text it
│ taken from the appropriate section of FILENAME.EXT. If
│ no file is specified, the ECHODESC.BBS in GTPATH will
│ be used.
│
│ The format of this is simple.
│
│ Exx/yyy
│
│ details of the echo
│
│ Exy/yyz ( next echo number )
│
│ for Exx/yyy all text between Exx and Exx/yyz will be
│ put in WELCOME.BSS
│
│ The echo numbers must be in column one with no other
│ text on the line. Other than that the text is lifted
│ verbatim.
│
│ This option isn't particularly fast, but will do the
│ job, and afer all, it's not often that you would have
│ to do this anyway.
│
│ ECHODESC.BBS is a perfect source for these details.
│ In fact it's existence led me to doing this bit.
│ /new when used with /WELCOME
│ this will write only new WELCOME.BBS files, and will
│ not overwrite any pre-exisitng WELCOME.BBS that you
│ may have already seat up.
│ when used with /SPLIT
│ will check the specified directory for each of the
│ entries in ROUTING.BBS, and offer the option for you
│ to create the directory.
│ Also applies to /BUILD when RTG2MDR.WRK is empty and
│ /BUILD does a split.
│ When a directory has been determined as missing, you
│ will be prompted to create it, skip over this one,
│ create this and all further missing directories, and
│ finally you can ignore this one, and all further ones.
/old[nn] checks MAILIN to determine last bag delivered for each
echo and copies entries in GTMDIR.BBS which are older
than nn days to GTMDIR.OLD
NOTE if no qbags are found, it will be assumed that
this is a new echo.
/* NOT YET AVAILABLE */
Config file
The config file - which must be located in the GTPATH directory -
RTG2MDIR.CFG has the following structure
DEFAULT=d:\path\name.ext
MAILDRIVE=d:
EXTENSIONS this MUST be on first column
NET
LOC
E00
E01
E02
E03
E05
E06
E10
E30 This comment appears in composite GTMDIR
END
ACCESS = A
the extensions are in the order in which the GTMDIR.ext files
are to be concatenated. If the extension is not found in this
file, then it will not be included in the concatenated file
created with the /build switch.
This file is fairly free format, any text after the data is
│ disregarded and can be used as comments. Text following the
│ extensions in either the CATEGORIES or EXTENSIONS sections
│ will appear before the first message base in the composite
│ file. This allows you to add a little one liner comment at
│ the start of each section, this gives the users another way
│ of seeing what the echo subjects are.
│
│ Refer to the sample RTG2MDR.CFG enclosed in the ZIP.
If the /CAT switch has been used, I'd suggest that you enter
all the categories listed in ECHOLIST.BBS in RTG2MDIR.CFG
under the CATEGORIES section.
There is a special file created for those message areas that
are 'funny', i.e. may not be in the echolist or whatever. The
│ extension on this file is ".#_#".
Support
You can either netmail me on 013/300, or subscribe to
E03/607 UK Utilities Support
available from a hub near you now....
Timings
Running on an IBM PS/2 model 50, 10MHz with co-pro, this program
takes 1m21s to /SPLIT apart a routing file with 382 echoes listed.
ECHOLIST.BBS was available to supply the echo descriptions.
/WELCOME switch run on same PC, 43 secs, to write WELCOME.BBS for
128 echoes, including creating directories, with 60 echoes
having no description found.
/BUILD took 1m43s, creating GTMDIR with 241 echoes listed.
Restrictions
Only 400 echoes currently supported, this includes those listed
in ECHOLIST.BBS, so if ECHOLIST.BBS gets any larger......
Path to message base no more then 30 chars and must include the
drive letter.
Echo description no more then 60 characters, the description in
ECHOLIST.BBS is less than this.
Will run with down to 180K of RAM free.
Revision History
V1.00 19/02/91 initial release
v1.10 20/02/91 8 hrs later Perry changed the format of the
ECHOLIST.BBS file. Thanks Perry.... <grin>
Gave an excuse to add the /CAT switch.
This version will work with both formats of
ECHOLIST.BBS
1.11 21/02/91 source rationalisation - not released.
1.12 22/02/91 now takes comments following extension in
RTG2MDIR.CFG and places them in the composite
routing file at the start of each section.
fixed small bug with Netmail/Private/Public
message bases.
added /WELCOME and /NEW, to place WELCOME.BBS
in the message directories.
1.13 23/02/91 /WELCOME is a tiny bit faster now. Was taking
several minutes ( 18m on my PC ), now down to
about 15s.
/NEW will check for message directories when
used with /SPLIT, and prompt user to create
it.
1.14 07/03/91 all this stuff about registration, and it did
not work properly. It does now!
Improved parameter validation.
Now distributed as RTMDRxxx.ZIP
Credits(?).
You, for giving this thing a try.
Scott Estes, The Sprawl 032/004 for ECHODESC ( GTEDxxyy.ZIP )
Perry Alexander, Infostation, 032/001 for ECHOLIST ( GTELxxyy.ZIP )
Oliver Bell, The Wind, 013.000 for help in distribution